翻訳と辞書
Words near each other
・ Enterprise (Via Rail train)
・ Enterprise (yacht)
・ Enterprise 2.0
・ Enterprise 2020
・ Enterprise Act 2002
・ Enterprise Allowance Scheme
・ Enterprise and Regulatory Reform Act 2013
・ Enterprise appliance transaction module
・ Enterprise application integration
・ Enterprise architect
・ Enterprise Architect (software)
・ Enterprise architecture
・ Enterprise Architecture Assessment Framework
・ Enterprise Architecture Body of Knowledge
・ Enterprise architecture framework
Enterprise architecture management
・ Enterprise architecture planning
・ Enterprise asset management
・ Enterprise Association of Regular Baptists
・ Enterprise Bank
・ Enterprise Bank Limited
・ Enterprise bargaining agreement
・ Enterprise bookmarking
・ Enterprise Building
・ Enterprise Building (High Point, North Carolina)
・ Enterprise Building (Worcester, Massachusetts)
・ Enterprise bus matrix
・ Enterprise Campaign Management
・ Enterprise Cape Breton Corporation
・ Enterprise Capital Fund


Dictionary Lists
翻訳と辞書 辞書検索 [ 開発暫定版 ]
スポンサード リンク

Enterprise architecture management : ウィキペディア英語版
Enterprise architecture management

Enterprise Architecture Management (or EAM) is a "management practice that establishes, maintains and uses a coherent set of guidelines, architecture principles and governance regimes that provide direction and practical help in the design and development of an enterprise's architecture to achieve its vision and strategy."〔F. Ahlemann et al. (eds.), Strategic Enterprise Architecture Management: Challenges, Best Practices, and Future Developments, Springer-Verlag Berlin Heidelberg, 2012〕
==Overview==
The fundamental prerequisites for effective EAM are a current, consistent baseline of information about the as-is landscape and an integrated planning process from demand to budget to reach the to-be landscape. The enterprise architecture function also involves reviewing and consolidating detailed architecture decisions and migration plans to identify efficiencies, advance standardization, and align business and IT priorities.
As IT architectural layers, business support processes, and organizational structures become more sophisticated and prone to constant change, EAM will only result in haphazard business and IT alignment if the primary focus is on delivering sets of technically based models. This approach is only helpful insofar as it depicts the enterprise architecture as a snapshot in time, but it offers no reiterative process support to develop architecture solutions and test against different scenarios, benchmarks, and standards as dictated by the ever converging business and IT strategy.
Moreover, a model-centric approach is prohibitively time-intensive to keep updated and leaves too much room for error as changes to the architecture occur unchecked and isolated in the heads of small groups of architecture specialists. Instead, the EAM effort has to bring the highly distributed knowledge of all experts to the table and allow every participant to provide such knowledge and input in the terms that best fit the experience and expectations of the contributing stakeholders.

抄文引用元・出典: フリー百科事典『 ウィキペディア(Wikipedia)
ウィキペディアで「Enterprise architecture management」の詳細全文を読む



スポンサード リンク
翻訳と辞書 : 翻訳のためのインターネットリソース

Copyright(C) kotoba.ne.jp 1997-2016. All Rights Reserved.